3.1.3.1.1. iTIP Testing

• All items in the iTIP testing scenarios passed with the following notes:

  • 4.1.1 create single event. Pass — Ran scenario by manually dropping a MIME file in the pickup folder of the transport log.

  • 4.1.5 Create an event using the Value parameter — day events always have a timezone associated with it.

  • RSVP responses to requests: client allows RSVP per email message and not per attendee. Other mail servers do not have any indication to show how whether a RSVP is required. One server sets the req and opt part as req participants — - this is a bug.

  • 4.2.4 Countering an Event — counter is not supported in one server

  • 4.2.5 Delegating an Event — the concept of delegates is different than that of RFC2445.

  • 4.3 — Publishing busy time — not supported

  • 4.4.6 — Add new instance to a recurring event: adding a single instance is not supported. The complete recurrence rule needs to be updated.

  • 4.4.7 — Add a new series of instances to a recurring event: Adding is not allowed. You can change the recurrence object completely. REFRESH is not supported.

  • 4.4.8 Counter an instance of a recurring event: Not supported

  • 4.7.2 Bad Recurrence-ID: If an invalid iCalender is received server fails the conversion of iCalendar and creates a simple IPM. Note message with the iCalendar body as an attachment.